Re: How to map http://www.myaddress.com to http://www.myaddress.com:8000 ?

No, there isn't. There are--or were--providers like dyndns that would also
do port and server re-mapping in addition to dynamic DNS aliasing.

Mike Hagerty wrote:

Hello.
Forgive me if this has been handled in the Archives. I've tried
searching different key words but I haven't
found anything.

I have an apache server running on port 8000.
This necessitates typing http://www.myaddress.com:8000 to get to my home
page.

I would like to be able to drop the ":8000" in the url and still have it
work.

The relevant parameters in /etc/apache/httpd.config seem to be:
Port 8000 - I set this to get around my company's firewall
#Listen - This is commented out, but from the apache docs, I think this
would just tell the server to listen on port 8000 (or the default 80)
but that the
port no. would still need to be specified in the url
request (?)
#NameVirtualHost *:80 - From the docs I can see how this can be used so
that a single apache server can handle web requests to different
ip:ports differently,
but I don't see how it could be
used for my purpose.

I guess I'm asking if there is any way to configure the server so that
http:/www.myaddress.com is assumed to be on port 8000 rather than 80 ?

Thanks!

-Mike

------------------------------------------------------------ ---------
The official User-To-User support forum of the Apache HTTP Server Project.
See for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org



------------------------------------------------------------ ---------
The official User-To-User support forum of the Apache HTTP Server Project.
See for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org

Re: How to map http://www.myaddress.com to

--0016e68ee039ff4cdc0480ac09cf
Content-Type: text/plain; charset=ISO-8859-1

On Sun, Feb 28, 2010 at 10:20 PM, Thomas, Peter wrote:

> No, there isn't. There are--or were--providers like dyndns that would also
> do port and server re-mapping in addition to dynamic DNS aliasing.
>
> Mike Hagerty wrote:
>
> Hello.
> Forgive me if this has been handled in the Archives. I've tried
> searching different key words but I haven't
> found anything.
>
> I have an apache server running on port 8000.
> This necessitates typing http://www.myaddress.com:8000 to get to my home
> page.
>
> I would like to be able to drop the ":8000" in the url and still have it
> work.
>
> The relevant parameters in /etc/apache/httpd.config seem to be:
> Port 8000 - I set this to get around my company's firewall
> #Listen - This is commented out, but from the apache docs, I think this
> would just tell the server to listen on port 8000 (or the default 80)
> but that the
> port no. would still need to be specified in the url
> request (?)
> #NameVirtualHost *:80 - From the docs I can see how this can be used so
> that a single apache server can handle web requests to different
> ip:ports differently,
> but I don't see how it could be
> used for my purpose.
>
> I guess I'm asking if there is any way to configure the server so that
> http:/www.myaddress.com is assumed to be on port 8000 rather than 80 ?
>
> Thanks!
>
> -Mike
>
> ------------------------------------------------------------ ---------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>
>
> ------------------------------------------------------------ ---------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>
If your port 80 is open then what's the great idea behind using port 8000
unless you want to run some caching proxy like SQUID.

--
Nilesh Govindarajan
Site & Server Administrator
www.itech7.com

--0016e68ee039ff4cdc0480ac09cf
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Re: How to map http://www.myaddress.com to http://www.myaddress.com:8000 ?

--Apple-Mail-1--830517990
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
charset=US-ASCII;
delsp=yes;
format=flowed

Hi.
As I stated, I am behind a firewall that is controlled remotely, so
port 80 is blocked (unless your come in from within our domain).
I have successfully run it for several years on port 8000 (any port >
1024 would do) but I would like to have
it so that the port number does not need to be specified by a user
wishing to access my site.
i.e., I want apache to reroute all traffic coming in on the (httpd)
default port 80 to port 8000.

I don't know if this is something apache can do (i.e., if it can
change the default port for http://www.mysite.com from 80 to 8000)
or if I need to accomplish it outside of apache (find some software
that maps port 80 to port 8000) ?

I'm kind of surprised (doubtful) that I would be the first person to
ask this -- other sites that have to use higher ports must wonder if
the added
burden of remembering/typing the port no. in the url deters users
from finding their site (?)

Thanks for your help,

-Mike

On Feb 28, 2010, at 11:57 AM, Nilesh Govindarajan wrote:

> On Sun, Feb 28, 2010 at 10:20 PM, Thomas, Peter
> wrote:
> No, there isn't. There are--or were--providers like dyndns that
> would also
> do port and server re-mapping in addition to dynamic DNS aliasing.
>
> Mike Hagerty wrote:
>
> Hello.
> Forgive me if this has been handled in the Archives. I've tried
> searching different key words but I haven't
> found anything.
>
> I have an apache server running on port 8000.
> This necessitates typing http://www.myaddress.com:8000 to get to my
> home
> page.
>
> I would like to be able to drop the ":8000" in the url and still
> have it
> work.
>
> The relevant parameters in /etc/apache/httpd.config seem to be:
> Port 8000 - I set this to get around my company's firewall
> #Listen - This is commented out, but from the apache docs, I think
> this
> would just tell the server to listen on port 8000 (or the default 80)
> but that the
> port no. would still need to be specified in the url
> request (?)
> #NameVirtualHost *:80 - From the docs I can see how this can be
> used so
> that a single apache server can handle web requests to different
> ip:ports differently,
> but I don't see how it could be
> used for my purpose.
>
> I guess I'm asking if there is any way to configure the server so that
> http:/www.myaddress.com is assumed to be on port 8000 rather than 80 ?
>
> Thanks!
>
> -Mike
>
> ------------------------------------------------------------ ---------
> The official User-To-User support forum of the Apache HTTP Server
> Project.
> See for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>
>
> ------------------------------------------------------------ ---------
> The official User-To-User support forum of the Apache HTTP Server
> Project.
> See for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>
> If your port 80 is open then what's the great idea behind using
> port 8000 unless you want to run some caching proxy like SQUID.
>
> --
> Nilesh Govindarajan
> Site & Server Administrator
> www.itech7.com
>


--Apple-Mail-1--830517990
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=US-ASCII

-webkit-line-break: after-white-space; ">
Hi.

Re: How to map http://www.myaddress.com to

On Sun, Feb 28, 2010 at 2:56 PM, Mike Hagerty wrote:

> I'm kind of surprised (doubtful) that I would be the first person to ask
> this -- other sites that have to use higher ports must wonder if the added
> burden of remembering/typing the port no. in the url deters users from
> finding their site (?)

You're not. If you can't receive traffic on port the default port, you
can't receive traffic on the default port.

--
Eric Covener
covener@gmail.com

------------------------------------------------------------ ---------
The official User-To-User support forum of the Apache HTTP Server Project.
See for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org

Re: How to map http://www.myaddress.com to

On Sun, Feb 28, 2010 at 2:56 PM, Mike Hagerty wrote:

> I don't know if this is something apache can do (i.e., if it can change t=
he
> default port for http://www.mysite.com from 80 to 8000)
> =A0or if I need to accomplish it outside of apache (find some=A0software =
that
> maps port 80 to port 8000) ?

The browser decides what port to connect to, so it's far to late to do
anything in the webserver.

A third-party might be able to relay traffic for you, but at that
point you're probably better off hosting your content somewhere else.

--=20
Eric Covener
covener@gmail.com

------------------------------------------------------------ ---------
The official User-To-User support forum of the Apache HTTP Server Project.
See for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org

Re: How to map http://www.myaddress.com to http://www.myaddress.com:8000 ?

Okay, here is my limited understanding of apache ...
When you set the port to 8000 in /etc/apache/httpd.conf - you are
telling apache to listen on port 8000
for requests to serve, rather than on the default port (80).

However, this means that users must access your site by adding ":
8000" to the url in their browser.

I cannot use the default port (80) because it is behind a firewall at
the university where I work.
If I use that port, then I can access my site from an IP address
within our domain, but not from an outside
IP, which renders it useless to me. Presumably the firewall will not
allow communications to port 80 (or any port < 1024) on
any machine (other than their official servers I suppose) from an
outside IP.

When I say that I cannot receive traffic on the default port (80),
this is what I mean.

I guess the answer here is that there is no way around it - if a
browser does not specify the port in the url request,
then it will automatically send the request to port 80 on the server
and the firewall will block it before it reaches my server ...



On Feb 28, 2010, at 4:34 PM, Eric Covener wrote:

> On Sun, Feb 28, 2010 at 2:56 PM, Mike Hagerty wrote:
>
>> I'm kind of surprised (doubtful) that I would be the first person
>> to ask
>> this -- other sites that have to use higher ports must wonder if
>> the added
>> burden of remembering/typing the port no. in the url deters users
>> from
>> finding their site (?)
>
> You're not. If you can't receive traffic on port the default port, you
> can't receive traffic on the default port.
>
> --
> Eric Covener
> covener@gmail.com
>
> ------------------------------------------------------------ ---------
> The official User-To-User support forum of the Apache HTTP Server
> Project.
> See for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>


------------------------------------------------------------ ---------
The official User-To-User support forum of the Apache HTTP Server Project.
See for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org

Re: How to map http://www.myaddress.com to http://www.myaddress.com:8000?

On 28-Feb-10 12:56, Mike Hagerty wrote:
> I want apache to reroute all traffic coming in on the (httpd) default
> port 80 to port 8000.

How do you think apache is going to see any traffic on port 80 when your
firewall is blocking port 80?


--
She'd always tried to face towards the light. She'd always tried to face
towards the light. But the harder you stared into the brightness the
harsher it burned into you until, at last, the temptation picked you up
and bid you turn around to see how long, rich, strong and dark,
streaming away behind you, your shadow had become- --Carpe Jugulum

------------------------------------------------------------ ---------
The official User-To-User support forum of the Apache HTTP Server Project.
See for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org

Re: How to map http://www.myaddress.com to

--0016e68dd28453c0200480b3d661
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Mar 1, 2010 at 3:20 AM, Mike Hagerty wrote:

> Okay, here is my limited understanding of apache ...
> When you set the port to 8000 in /etc/apache/httpd.conf - you are telling
> apache to listen on port 8000
> for requests to serve, rather than on the default port (80).
>
> However, this means that users must access your site by adding ":8000" to
> the url in their browser.
>
> I cannot use the default port (80) because it is behind a firewall at the
> university where I work.
> If I use that port, then I can access my site from an IP address within our
> domain, but not from an outside
> IP, which renders it useless to me. Presumably the firewall will not allow
> communications to port 80 (or any port < 1024) on
> any machine (other than their official servers I suppose) from an outside
> IP.
>
> When I say that I cannot receive traffic on the default port (80), this is
> what I mean.
>
> I guess the answer here is that there is no way around it - if a browser
> does not specify the port in the url request,
> then it will automatically send the request to port 80 on the server and
> the firewall will block it before it reaches my server ...
>
>
>
>
> On Feb 28, 2010, at 4:34 PM, Eric Covener wrote:
>
> On Sun, Feb 28, 2010 at 2:56 PM, Mike Hagerty wrote:
>>
>> I'm kind of surprised (doubtful) that I would be the first person to ask
>>> this -- other sites that have to use higher ports must wonder if the
>>> added
>>> burden of remembering/typing the port no. in the url deters users from
>>> finding their site (?)
>>>
>>
>> You're not. If you can't receive traffic on port the default port, you
>> can't receive traffic on the default port.
>>
>> --
>> Eric Covener
>> covener@gmail.com
>>
>> ------------------------------------------------------------ ---------
>> The official User-To-User support forum of the Apache HTTP Server Project.
>> See for more info.
>> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
>> " from the digest: users-digest-unsubscribe@httpd.apache.org
>> For additional commands, e-mail: users-help@httpd.apache.org
>>
>>
>
> ------------------------------------------------------------ ---------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See for more info.
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> " from the digest: users-digest-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>
You need to use some port forwarding service like no-ip, etc. which will
work if and only if your machine has a public IP.

--
Nilesh Govindarajan
Site & Server Administrator
www.itech7.com

--0016e68dd28453c0200480b3d661
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable